I suspect that many of you are familiar with the term "hard coding a value" whereby the age of an individual or their location is written into the condition (or action) of a business rule (in this case) as shown below:

if customer.age > 21 and customer.city == 'denver'

then ...

Such coding practices are perfectly expectable provided that the conditional values, age and city, never change. They become entirely unacceptable if a need for different values could be anticipated. A classic example of where this practice occurred that caused considerable heartache in the IT industry was the Y2K issue where dates were updated using only the last 2 digits of a four digit number because the first 2 digits were hard-coded to 19 i.e. 1998, 1999. All was well provided that the date did not advance to a time beyond the 1900’s since no one could be certain of what would happen when the millennia arrived (2000). A considerably amount of work (albeit boring) and money, approximately $200 billion, went into revising systems by way of software rewrites and computer chip replacements in order to thwart any detrimental outcomes. It is obvious how a simple change or an assumption can have sweeping consequences.

You may wonder what Y2K has to do with Business Rule Management Systems (BRMS). Well, what if we considered rules themselves to be hard-coded. If we were to write 100s of rules in Java, .NET or whatever language that only worked for a given scenario or assumption, would that not constitute hard-coded logic? By hard-coded, we obviously mean compiled. For example, if a credit card company has a variety of bonus campaigns, each with their own unique list of rules that may change within a week’s time, what would be the most effective way of writing software to deal with these responsibilities?

We are not all equally motivated. Some people have more self-drive than other people. This is why we find that some people always end up at the top even when the odds are against them. An employee, with this realization, through the Human Resource department, should be able to design efficient career development systems. For this system to work, the employer must understand the nature of the business environment in which they are operating.

Why Train Employees?

The purpose of training employees is to enable them to grow with time and increase their efficiency. The business world is quite dynamic, nothing stays the same for long. Training one’s employees allows them to keep abreast with the ever changing technological advancements and many other factors that are relevant to his/her line of work. Employees cannot be expected to solve all their employer’s expectations with static skills and techniques. Even the most updated technology becomes obsolete at some point.
People are the biggest assets in organizations. For an establishment to flourish, it is important that the employer understands certain key things that help spur their development.

In a report from the Harvard Business Review, “The Impact of Employee Engagement of Performance,” the most impactful employee drivers are:

Smart Project Management –Best Practices of Good Managers

Project management could be one of the easiest jobs on the planet, and could also be the worst nightmare. The difference between the two extremes depends on smart management of a project. According to the project management institute, there are five phases in project management - Initiating, Planning, Executing, Monitoring & Controlling, and Closing.

Every manager has his own style of project management. But there are a lot of contributing factors that result in a successfully managed project. These factors vary from project to project, but they all contain some common elements.

1. Setting SMART Goals

I’ll get straight to the point.  Why should companies invest more in management training?  Here are 10 simple reasons.

1) An employee’s relationship with his or her direct manager is the most important single factor in employee engagement.

2) Engaged employees are happier and more productive.  Disengaged employees are frustrated and more disruptive.

3) Because there’s no widely agreed-on skillset for management (good managers come in all shapes and sizes), there’s an assumption everyone knows how to do it.  This is akin to someone who’s never driven before being given keys to a car and told: “Drive.”  (Many many years ago, this is how I first learned to manage.  I blundered my way through it.  Trial and error.  It wasn’t pretty.)